Enabling ASP Error Processing

By default, the "default web site" and all its applications will transfer the processing of ASP errors to the 500-100.asp file; however, any new web site created by the user or its applications will transfer the processing of 500;100 errors to Default and not a custom error file. If you want to develop additional error processing for .asp files, you can do so by either mapping the 500-100 error to the 500-100.asp file, or by creating an error-processing .asp file of your own.

The 500-100.asp file processes any errors that occur during compilation or running of .asp files. When an ASP error occurs, IIS returns the 500-100.asp file with detailed information about the error, such as the line number in which the error occurred and a description of the error.

If you create an ASP error-processing file of your own, you will then need to enable the custom error file in the IIS snap-in. See Adding a Custom Error Message for more information.

For information on how to use the ASPError object for ASP error processing, see the ASPError reference page.

Notes

If the file 500-100.asp itself contains ASP errors, ASP will not return another 500-100.asp file; instead, the error will be reported as if no custom error file exists for 500-100 errors.
If the error-processing file (by default, 500-100.asp) contains run-time errors then only this error will be displayed regardless of the type of error in the requested .asp file. If the error-handling file has preprocessor or compilation errors then both errors will be displayed in the browser (that is, the error from the 500-100.asp file as well as the error in the requested .asp file will be displayed).